Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[unix x86] Fix GCMemoryInfoData size assertion #59417

Merged
merged 1 commit into from
Sep 21, 2021
Merged

[unix x86] Fix GCMemoryInfoData size assertion #59417

merged 1 commit into from
Sep 21, 2021

Conversation

t-mustafin
Copy link
Contributor

Fixes assertion on linux x86 after #58738:

Assert failure(PID 13816 [0x000035f8], Thread: 13816 [0x35f8]): Consistency check failed: Managed object size does not match unmanaged object size
man: 0x110, unman: 0x114, Name: System.GCMemoryInfoData
FAILED: size == expectedsize
    File: /home/tmustafin/dotnet/runtime/src/coreclr/vm/binder.cpp Line: 556
    Image: /home/tmustafin/dotnet/runtime/artifacts/bin/coreclr/Linux.x86.Checked/corerun

Aborted (core dumped)

cc @jkotas @MichalStrehovsky @gbalykov @alpencolt

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost added the community-contribution Indicates that the PR has been added by a community member label Sep 21, 2021
@jkotas jkotas merged commit 7d7b56e into dotnet:main Sep 21, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
@t-mustafin t-mustafin deleted the Fix_GCMemoryInfoData_assertion branch August 10, 2023 14:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@jkotas jkotas jkotas approved these changes

Assignees
No one assigned
Labels
community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@t-mustafin @jkotas